Repository navigation
Design + plan: per-thread read-only reach into another project (#109) - #119
Merged
currentbits merged 8 commits intoAug 16, 2026
Merged
Conversation
… Update-check failures are invisible — unhandled rejection, s
… Desktop-notification preference: global toggle and per-threa
… Composer is hard-disabled during runs — allow type-ahead / q
… Synchronous git on the main-process event loop with no defau
… Web-server port conflict silently kills app boot — no window
… Merge conflicts auto-abort and surface raw git stderr — no r
Second half of #109: the read-only "go look at how X does this" case the spawn-guard PR deferred. Per-thread opt-in list of readable projects, a read-roots sentence in the dispatched prompt, and a claude auto-allow for read-shaped tools under those roots. Writes stay in the owning project. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Six tasks: pure path/tool policy helper, readProjectIds field + setter + root resolution, read-roots sentence in the dispatch note, claude auto-allow, Read access submenu, full-suite gate. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
currentbits
deleted the
coder/cross-project-spawns-a-thread-can-start--c056ca
branch
October 3, 2026 16:07
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design and implementation plan for the half of #109 that PR #111 deferred: letting a thread read another project's checkout ("go look at how project X does this") without ever writing there. Docs only — no code changes in this PR.
Why this shape
The obvious assumption for a feature like this is that there is a sandbox to open. There is not, and that reframed the design:
electron/providers.js:275,:393,:475— each documented in the file's own comments). They can already read and write any repo on this disk.--permission-prompt-tool stdio, routed to the UI atelectron/runner.js:1667), so it is the only one where an out-of-cwd read costs a click per file.So this feature grants no capability that is not already there. What it adds is the agent being told which other checkouts exist and that they are read-only, and — on claude — reads under those roots not stopping the run.
--add-diris deliberately not used anywhere: it makes a directory a full workspace dir, which grants writes.What the design specifies
readProjectIds— a per-thread opt-in list, set from a "Read access" submenu in the existing thread overflow menu. Forks inherit it, likepermissionMode.readRootsFor— resolves ids to on-disk roots, dropping deleted and remote-host projects at read time rather than by migration.[Read access]sentence in the prompt note every dispatch already carries, naming each root. Ungated; the existing[Thread]sentence keeps itscoder-threadsgate.autoAllowRead— on claude, auto-answersallowforRead/Grep/Glob/NotebookReadwhose paths resolve under a root.Edit,Write,Bashand anything unrecognised still prompt, so a write into another repo remains a decision the user is shown and makes.Known ceiling
On grok, kimi and opencode "read-only" is a sentence in the prompt and nothing more — those CLIs have no permission channel to enforce it. Stated in the spec and marked with a
ponytail:comment, same as the existingassertSameProjectceiling from #111.Files
docs/superpowers/specs/2026-08-16-cross-project-read-reach-design.mddocs/superpowers/plans/2026-08-16-cross-project-read-reach.md— 6 TDD tasks with the failing test written out for eachImplementation has not started; merging this locks the approach, not the code.